SparkN0de-git - /page/commit.mu

Micron Document

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

| SparkN0de-git | SparkN0de |

Node / ReticulumProjects / MeshChatX.git / commits / decf1aa

Commit decf1aa2c016ad8e4563f5bb67590ed95405ed70

󰉖 Browse tree at this commit

Parents : 990aba5

Author : Ivan <ivan@quad4.io>

Signature : Signature validation error

Date : 2026-05-09T22:23:53-05:00

fix(FAQ): typo

Changes

1 files changed, 1 insertions(+), 1 deletions(-)

M FAQ.md +1 -1

Diff

diff --git a/FAQ.md b/FAQ.md

index f359e04b..2682cc22 100644

--- a/FAQ.md

+++ b/FAQ.md

@@ -8,7 +8,7 @@ Grow some patience, send it to a propagation node, and chill. Sometimes I go off

**Why did you create MeshChatX?**

-I noticed Liam Cottle became busy with MeshChat stuff, but I also wanted something modern and easier to use for myself and some friends. Eventually more people discovered my fork and started using it. I have since reworked the architecture and modernized most of the frontend and backend. I am not a fan of Electron, but I do what I can to make it a worthy Electron application by taking advantage of everything it has to offer, from packaging to security and integrity.

+I noticed Liam Cottle became busy with MeshCore stuff, but I also wanted something modern and easier to use for myself and some friends. Eventually more people discovered my fork and started using it. I have since reworked the architecture and modernized most of the frontend and backend. I am not a fan of Electron, but I do what I can to make it a worthy Electron application by taking advantage of everything it has to offer, from packaging to security and integrity.

**Will MeshChatX move to a different implementation?**

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────